Configuring the Sametime Proxy server to only connect to specific Community servers in a Sametime Community

Hotfix # TPAE-8LNJ33 Created By Tony Payne/Lexington/IBM on 09/13/2011 at06:26 AM

Description of Problem and how Fix addresses it:

In some deployment scenarios - it may be desirable to have the STProxy server only communicate with certain members of a community cluster - The current 'clusterlist' item in the stproxyconfig.xml file does not allow for this.

The clusterlist works by comparing the name of the cluster a given server belongs to with the names in the list - if there is a match, the server is added to the 'available' list, otherwise not.

In a scenario where there is no Community Cluster defined - each server's 'cluster' is its own CN (cn=server/o=org) - so you can define which individual servers to access using it. As soon as a cluster is defined, the clustername is what is compared.

This workaround extends this by adding a second check against the servers FQDN (community.server.com) and adding any matches to the available list.

To determine the appropriate host names to add, review the system out files from the STPRoxy server logs looking for a section similar to:

[9/3/11 0:30:15:767 EDT] 00000026 STConfigurati I com.ibm.rtc.stproxy.server.config.STConfigurationReader Community Server:  groupPath: \SametimeCommunity\Cluster\Servers\stcluster\chat.company.com\STIM01WIN.COMPANY.COM
serverFQDN: STIM01WIN.COMPANY.COM
cluster: stcluster
serverURL: 192.168.1.2
[9/3/11 0:30:15:783 EDT] 00000026 STConfigurati I com.ibm.rtc.stproxy.server.config.STConfigurationReader Community Server:  groupPath: \SametimeCommunity\Cluster\Servers\stcluster\chat.company..com\STIM02WIN.COMPANY.COM
serverFQDN: STIM02WIN.COMPANY.COM
cluster: stcluster
serverURL: 192.168.1.23
[9/3/11 0:30:15:783 EDT] 00000026 STConfigurati I com.ibm.rtc.stproxy.server.config.STConfigurationReader Community Server:  groupPath: \SametimeCommunity\Cluster\Servers\stcluster\chat.company.com\STIM03WIN.COMPANY.COM
serverFQDN: STIM03WIN.COMPANY.COM
cluster: stcluster
serverURL: 192.168.1.14
[9/3/11 0:30:15:783 EDT] 00000026 STConfigurati I com.ibm.rtc.stproxy.server.config.STConfigurationReader Community Server:  groupPath: \SametimeCommunity\Cluster\Servers\stcluster\chat.company.com\STIM04WIN.COMPANY.COM
serverFQDN: STIM04WIN.COMPANY.COM
cluster: stcluster
serverURL: 192.168.1.119
[9/3/11 0:30:15:783 EDT] 00000026 STConfigurati I com.ibm.rtc.stproxy.server.config.STConfigurationReader Community Server:  groupPath: \SametimeCommunity\Cluster\Servers\stcluster\chat.company.com\STIM05WIN.COMPANY.COM
serverFQDN: STIM05WIN.COMPANY.COM
cluster: stcluster
serverURL: 192.168.1.120

And add the 'serverFQDN' of the server(s) you want to have the STProxy connect to (separated by a comma)  to the 'clusterlist' definition in the stproxyconfig.xml file(s) on your stproxy servers -

	<clusterlist>STIM03WIN.COMPANY.COM,STIM05WIN.COMPANY.COM</clusterlist>